Littlefool
Nuke Newbie
Posts:3
 |
| 10/01/2007 7:10 AM |
|
Hi, I'm encountering this problem and found many posts about the same problem but without much helping information for me. I have developed a small application which will grow in the future using DNN on my local developer machine (Server 2003, IIS6). Everything from installation, configuration till developing went fine. Now we need to install it on the test server to start our testing sequence before release. The test server is the same environment as my developing machine (server 2003 with IIS6). I performed exact the same steps as I did on my machine (unzipping the install file, creating new web site in IIS, set NETWORK SERVICE user and permissions, Default.aspx as home...) Yet when I try to access it, I get following error:
| |
The website declined to show this webpage |
<!-- This row is for HTTP status code, as well as the divider-->
| HTTP 403
| <!-- Error Body -->
| |
Most likely causes:
- This website requires you to log in.
| <!-- What you can do -->
| |
What you can try: | <!-- back to previous page -->
| |
| <!-- InfoBlock -->
| |
This error (HTTP 403 Forbidden) means that this program was able to connect to the website, but it does not have permission to view the webpage. | When I try to access the Default.aspx page directly, I receive following error:
Server Error in '/' Application.
The resource cannot be found. Description: HTTP 404. The resource you are looking for (or one of its dependencies) could have been removed, had its name changed, or is temporarily unavailable. Please review the following URL and make sure that it is spelled correctly.
Requested Url: /Default.aspx
I am out of resources, our installation expert is out of resources and we also put out our network manager here at the office. Without this working, we can't start testing, can't deploy it and our support won't be able to start their work and project running... So a lot of pressure is comming on my shoulders.
Any response is extremely welcome to me.
Thanks |
|
|
|
|
Joseph Craig
DNN MVP
Posts:11667
|
| 10/01/2007 9:50 AM |
|
It's difficult to diagnose without being able to see the site. I would suggest that you review these two tutorials: There are others in the sequence of tutorials for site owners and administrators, too. You might also try this: Drop a simple "under construction" page named app_offline.htm into the root directory of the site that is causing you trouble. Do you see that file if you browse to the site? If you see it, and you don't see the DotNetNuke site with that file remove, then your problem is more likely with the DotNetNuke installation. If you don't see the app_offline.htm file, then your problem has to do with configuring the web site itself. In that case, look at IIS, DNS, etc. |
|
Joe Craig, Patapsco Research Group
Complete DNN Support |
|
|
Lee Sykes
DNN Creative Staff
Nuke Master VI
Posts:4945
|
|
Littlefool
Nuke Newbie
Posts:3
|
| 10/02/2007 1:15 AM |
|
Thanks for your replies. After a whole day fooling around with it, we ended up finding the reason (and solution) by 5 o'clock or so. Turned out that the ip address that was assigned for using with this site, was already in use somewhere else where it didn't supposed to be. So, that's what we call a whole day well spend, and at 5 I could start configuring DNN, installing the skins and modules, creating the pages and make everything ready for testing ;) Still very happy that it turned out working, or I entered into big problems ;) So, for people having the same errors here... check the use of your ip address and make sure it's available  |
|
|
|
|
Lee Sykes
DNN Creative Staff
Nuke Master VI
Posts:4945
|
|
Tyler R
Nuke Newbie
Posts:2
|
| 10/08/2007 11:34 AM |
|
We're hitting this error on our hosting provider. If this post should be a new thread, please move this...
We have a DNN 4.5.5 site set up and running. When we registered our domain name and created the domain name as a portal alias for the site, we get a 403.1 - Forbidden: Execute access is denied error.
We can get to the site if we go to the domain name/Home/tabid/36/Default.aspx, so I temporarily set up an index.html page in the root that does a redirect to that address.
Is this a DNN config issue or a web hosting issue?
Thanks for any help on this!!
|
|
|
|
|
Joseph Craig
DNN MVP
Posts:11667
|
| 10/08/2007 11:51 AM |
|
It sounds more like a file permission error. The "access is denied" is the clue that I'm looking at.
But, part 2 is confusing. I'd guess that it's still a permission error, but related to the site with the actual domain name. Make sure that IIS has the correct permissions for that site.
(Third guess) If the only change is related to portalalias, then the problem could be your DNS for the new address ... |
|
Joe Craig, Patapsco Research Group
Complete DNN Support |
|
|
Tyler R
Nuke Newbie
Posts:2
|
| 10/08/2007 1:05 PM |
|
Is there a way that there would be different file permissions when the domain name and the original address we installed DNN on are on the same IP address?
Something in IIS could be set that the domain name lost rights to .aspx files?
Thanks for the quick response! This has been giving me some headaches.
-Tyler |
|
|
|
|
Joseph Craig
DNN MVP
Posts:11667
|
| 10/08/2007 2:05 PM |
|
I don't know the answers to your questions. But, this should be something that your hosting provider can investigate. |
|
Joe Craig, Patapsco Research Group
Complete DNN Support |
|
|
Aymen
Nuke Newbie
Posts:4
|
| 11/22/2007 10:36 AM |
|
Hello,
I have a question please. Is the Ip adresse that we configure in the Web.conf, is it related to the server? or we should assign an other IP adress for the web site. How it works?
I have the same problem.
Thank you for your help.
Aymen |
|
|
|
|
Joseph Craig
DNN MVP
Posts:11667
|
| 11/22/2007 10:42 AM |
|
If you are asking about the IP address in the connection string, that is the IP address of the SQL Server. It is needed so that DotNetNuke can connect to the database. You must use either the IP address of the name of the SQL server computer.
As for assigning an IP address to your web site, the connection of the IP address to the domain name of your site should be done in the DNS setup of your site. This is completely separate from the DotNetNuke installation. |
|
Joe Craig, Patapsco Research Group
Complete DNN Support |
|
|
Aymen
Nuke Newbie
Posts:4
|
| 11/23/2007 9:17 AM |
|
Tkank Very much Joe,
I will verify the settings of my website. Hope that it will work.
Have a good day and thnak you again for your help. I appreciate it.
Aymen |
|
|
|
|
Aymen
Nuke Newbie
Posts:4
|
| 11/26/2007 11:29 AM |
|
I have deployed my dotnetnuke website on an SQL server 2005 and Windows server 2003.
When I put the URL of the website which was specificated as an Alias, The web browser made a redirection to the local alias (localhost).
What kind of problem do I have? And what could be wrong in my website configuration?.
I would be gratefull if you could help me.
Sincerely,
Aymen |
|
|
|
|
Joseph Craig
DNN MVP
Posts:11667
|
| 11/26/2007 4:11 PM |
|
You probably didn't adjust the portalalias table to point to the correct site. Review these tutorials |
|
Joe Craig, Patapsco Research Group
Complete DNN Support |
|
|
Littlefool
Nuke Newbie
Posts:3
|
| 11/27/2007 12:50 AM |
|
Hi, the same problem during our latest DNN installation. We found out that there were no PortalAlias for anything other than Localhost in the DNN database.
By changing this to the web address, the problem was fixed. |
|
|
|
|
Aymen
Nuke Newbie
Posts:4
|
| 11/27/2007 2:40 PM |
|
Thank you very much for your post. I will verify the portalalias table. Hope that will fix the problem.
Have a good day.
thanks.
Aymen |
|
|
|
|